Lose connection to database = close dxl window automatically

I have been running into this problem and maybe the best solution is not to use the awful built in DXL editor. But whenever their is a connection loss to the doors database it closes the DXL interaction window automatically without a prompt to save the code. Which has ended up in me losing 15-20 minutes of coding numerous times.

Now obviously I can just use a txt editor but in my opinion there should at least be a prompt to save the dxl program. Any thoughts?
TheDrizzle - Tue Jul 12 11:27:49 EDT 2011

Re: Lose connection to database = close dxl window automatically
llandale - Tue Jul 12 12:05:37 EDT 2011

Not sure that an abort 'should' be so nice. The same thing happens with exception violations. The solution, of course, is to save before Run.

I notice that if you use a Text editor, you will of course save before Run, otherwise you get the old code.

For any advanced text editor, better than Notepad, its far better to develop in the Editor and simply "#include" the file from the DXL window. Others here argue in favor of using the slick Editor to "send" the file to DOORS and "retrieve" the results, but I find that its easier to place the correct context with the DXL window (e.g. from the specific open module with the specific object already selected). And because I'm pretty much set in my ways.

Louie

I use the #include for any code that I may remotely want to save. I edit a "temp.dxl" file and #include it, and protect myself from the numerous exception violations I seem to get.

Re: Lose connection to database = close dxl window automatically
SystemAdmin - Tue Jul 12 12:19:38 EDT 2011

Have a look at the DXL Editor (www.dxleditor.com).
Using this you can start DOORS scripts and catch the results directly out of the editor.